All values listed below will be created during the installation of the WinMux2k driver. The settings are provided by the winmux2k.inf file. If you want to write your own preferences to the Registry you can edit the inf file before installing the driver.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ATAT&S0 AT\Q3 AT+ICF=3 AT+CMUX=0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If the number of TotalChannels is greater than VirtualChannels and no VirtPortX value for additional channels is defined, these additional ports are not visible as COM ports. They can be accessed by the link named SERMUX_CONTROL_PREFIX defined in sermux_i.h. This allows to hide virtual ports to the user. Each physical port can have one hidden port.
|
|
|
|
|
|
|
|
|
|
|
|
0 Default for XC18The driver does not try to reconnect to the module if DSR changes. This feature can be switched off if an application controls the DSR line with AT&S.
1 Default for all modules except XC18The driver tries to reconnect to the module if DSR changes. The driver can detect if the module was disconnected and reinitializes it before the first data errors occur.
|
|
|
|
|
|
|
|
|
|
|
|
The command AT+CFUN=0 has been chosen as factory default for compatibility with older Siemens products. If you prefer to use one of the more efficient CYCLIC SLEEP modes it can be replaced with AT+CFUN=5 or 6 or 7 or 8 or 9. See [3] and [4] to verify the SLEEP mode types supported by your product. To avoid editing the Windows Registry you can alter the corresponding parameter in the winmux2k.inf file and then reinstall the driver.
|
|
|
|
|
|
|
|
0 Default for TC45 and XC18The driver does not wait for the DSR signal to go low when the module is shut down. Instead, the parameter RecoverTime (see below) is used.
1 Default for all modules except TC45 and XC18The driver waits for the DSR signal to go low when the module is shut down. In this case the parameter RecoverTime is not used. If the module is not switched off with the AT commands defined in the parameter ClosePort this parameter must be set to 0.
|
|
|
|
|
|
|
|
If the connected module only supports the Multiplexer Protocol version 2 this value is not used. If the supported Multiplexer Protocol version is 3 or higher, the multiplex power control is used instead of the values “PowerCmdPort” and “PowerDown”. In this case this value corresponds to the power down command of the multiplex power down frame described in [5]. If the value is greater than 255 there is no power down frame sent for Multiplexer Protocol 3.
|
|
|
|
|
|
This registry value provides the possibility to force the driver to use a lower multiplex protocol version than the maximum supported. The multiplex protocol has been improved continuously by adding several features. The multiplex protocol version is negotiated with the connected module during multiplex startup. It is used to ensure compatibility between different multiplex driver and module generations. The registry value isn’t mandatory, by default the WinMux driver uses always the latest protocol implementation with all available features. If for some reason an older multiplex protocol shall be used it can be controlled with that registry value. For further information about the multiplex protocol versions refer to the “Multiplexer User’s Guide”.
|
|
|
|
Modules with multiplex protocol version 4 and above use a kind of HDLC framing to secure the data transmission on the virtual ports and avoid data loss at high transfer rates and much data traffic. This registry value provides the possibility to adjust the size of the HDLC window which defines the maximal number of outstanding HDLC packets. It can be between 2 and 7.
|